Repository navigation
docs: doc-review 2026-10-14 — investigation entries, alert-aggregation rework, label panel, dashboard and RUM drift - #1053
Merged
Conversation
added 2 commits
October 14, 2026 08:37
![flashduty[bot]](https://github.githubassets.com/images/gravatars/gravatar-user-420.png){kind=avatar}
…n rework, label panel, dashboard and RUM remote-config drift Window: 2026-10-13T08:11:02Z .. 2026-10-14T08:11Z (diff mode, 23 repos scanned). 42 findings (3 high / 31 medium / 8 low); 37 pages edited (zh + en), 1 new page (monitors/alert-rules/investigation-entries) registered in docs.json.
…icense types; restore source-verified HarmonyOS SDK version gates - platform/pricing: the per-period release cap applies to releasing a fixed or a temporary License (enforced per account in fc-event logic/resource/usage.go), so move it out of the 临时 License tab into a type-agnostic Note. - rum: keep the HarmonyOS remote-config / sessionOnError version gates (0.6.0 / 0.7.0) — verified against fc-sdk-harmony tags harmony-sdk-v0.6.0 and harmony-sdk-v0.7.0.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Doc Review — 2026-10-14
Mode: diff (since 2026-10-13T08:11:02Z — the previous successful run — through 2026-10-14T08:11Z)
Findings: 42 total — 3 high, 31 medium, 8 low
Repos scanned: 23 (all source repos in
mapping.yaml+ the 6fc-foundation-appsubmodule repos, cloned as siblings)Branch:
doc-review/2026-10-14-081143Changes
monitors/quickstart/quickstart.mdxon-call/channel/create-edit.mdxon-call/incident/search-view-incident.mdxai-sre/im.mdxchangelog/changelog.mdxchangelog/changelog.mdxchangelog/changelog.mdxchangelog/changelog.mdxchangelog/changelog.mdxmonitors/dashboards/dashboards.mdxmonitors/dashboards/dashboards.mdxmonitors/dashboards/dashboards.mdxmonitors/explore/explore.mdxmonitors/explore/explore.mdxmonitors/alert-rules/active-alerts.mdxon-call/channel/noise-reduction.mdxon-call/channel/noise-reduction.mdxon-call/channel/noise-reduction.mdxon-call/channel/noise-reduction.mdxon-call/channel/noise-reduction.mdxon-call/channel/noise-reduction.mdxon-call/incident/what-is-incident.mdxon-call/incident/search-view-incident.mdxon-call/incident/what-is-incident.mdxon-call/configuration/schedule.mdxon-call/incident/alert-management.mdxplatform/team-members.mdxrum/quickstart/app-management.mdxmonitors/dashboards/dashboards.mdxmonitors/explore/explore.mdxdeveloper/go-sdk.mdxon-call/integration/alert-integration/routing-rules.mdxon-call/channel/noise-reduction.mdxon-call/channel/noise-reduction.mdxon-call/channel/noise-reduction.mdxrum/sdk/harmony/advanced-config.mdxAlso in this PR:
changelog/changelog.mdx(+ en)<Update label="2026-10-14">block with five sectionsmonitors/alert-rules/investigation-entries.mdx(NEW, zh + en)docs.jsonin both language treesplatform/pricing.mdx(+ en)Review checklist
monitors/alert-rules/investigation-entriespage is the biggest addition — review it firstmint broken-links(Mintlify v20 runtime):success no broken links foundCross-repo follow-ups (flashduty-website)
Five derivative findings target the website repo. Per the automation's rules they are not edited here;
each needs a website changelog entry (the site's
content/changelog/stops at 2026-10-05):content/changelog/2026-10-14-investigation-entries.mdx(+.zh.mdx) — the investigation-entries capability (rule-side 调查入口 → detail-side 排查入口).content/changelog/2026-10-14-alert-aggregation-methods.mdx(+.zh.mdx) — the three mutually-exclusive grouping methods and the new 告警聚合 wizard step.content/changelog/2026-10-14-incident-label-panel.mdx(+.zh.mdx) — the label-panel rework (系统标签, 相关链接 bar, richer value rendering, 去查询 icon removed).content/changelog/2026-10-14-schedule-notify-cycles.mdx(+.zh.mdx) — 定时通知 gained 每天 / 每周 / 每月 cycles.content/changelog/2026-10-14-dashboard-global-search.mdx(+.zh.mdx) — dashboard global search and the panel-editor changes.Website integrations catalog: no follow-up — no window feature is an alert-source/tool integration and no integration-count claim drifted.
Corrections made during review (worth a second pair of eyes)
platform/pricing.mdxsat inside the 「临时 License」 tab while enforcement counts releases per account regardless of license type (fc-event logic/resource/usage.go:102,644=LicenseCnt × 10per window; member removal bypasses it —cmd/server/controller/license/inter.go:86-88). Moved to a type-agnostic<Note>after the tabs; the numeric multiplier is deliberately not published.0.6.0for console remote configuration and0.7.0forsessionOnError. These were briefly removed during review as unverifiable, then restored:fc-sdk-harmonytagharmony-sdk-v0.6.0is the first tag containingbbc40cf("Read the console's sampling settings on HarmonyOS"), andharmony-sdk-v0.7.0is the first containingcd92a56("add sessionOnError …"). That repo is not inmapping.yaml, which is why the first search missed it.> 0; the code isbefore >= 0 && after >= 0 && before + after > 0(pages/rule/investigation.ts). The new page and the changelog follow the code.Mapping warnings
fc-foundation-app→src/Packages/ai-sreis a gitlink (ai-sre-web); the mapped sub-pathsrc/Packages/ai-sre/srcwas analyzed from a sibling clone ofai-sre-web.derivative_surfaces.comparison_page.pathspoints atzh|en/on-call/quickstart/comparison.mdx, which does not exist. The real comparison pages arezh|en/on-call/comparison/vs-pagerduty.mdxandvs-opsgenie.mdx; the derivative pass was run against those, but the registry entry should be corrected in the skill'smapping.yaml.meow-ui(a submodule offc-foundation-app, 67 changed files this window) is referenced by no module inmapping.yaml, so none of it was analyzed. Shared console code underfc-foundation-app/src/components/**(TimeRangepicker grew ~1093 lines this window) is likewise unmapped — that is why no finding covers it.monit-webapichanged exactly one file in the window (misc/plan/dashboard/product/requirements.md, internal product-planning text); its paths are mapped, so it was scanned and produced no finding.Skipped
| **排查入口** | 告警规则可预置仪表盘 / 查询工作台入口（含变量与时间范围），故障与告警详情按触发时的快照一键直达观测 | … |— apply to the §Response table ofzh|en/on-call/comparison/vs-pagerduty.mdxandvs-opsgenie.mdxonce the competitor cells are confirmed against public sources.LicenseListResponseinapi-reference/on-call.openapi.{{zh,en}}.jsondocuments onlytotal+itemsand now lacks the newrelease_limitedfield (fc-foundation-app/src/pages/Access/service.ts:21-25). This is api-review's surface, so it was left to that automation rather than hand-edited here.Known conflicts with open PRs
doc-review/2026-10-12-080816, still open) inserts its own<Update>block at the same position inzh|en/changelog/changelog.mdx(its hunk covers old lines 4-9, ours inserts at line 7). Expect a merge conflict in the changelog when both are merged; the two blocks are independent content.zh|en/ai-sre/im.mdx(it only removesGet). Our change rewrites all three rows to the current pools, so that table will conflict; ours is the version that matchesfc-event@origin/main.zh|en/on-call/incident/search-view-incident.mdx(docs: doc-review 2026-10-12 — RUM auto-analysis, AI SRE IM attachments, CLI --fields, incident/integration/monitors drift #1045 touches ~line 250, the timeline event-type table; our edits are at lines 140-195) andzh|en/monitors/dashboards/dashboards.mdx(docs: doc-review 2026-10-12 — RUM auto-analysis, AI SRE IM attachments, CLI --fields, incident/integration/monitors drift #1045 touches ~line 195; our edits are at 20, 66, 73, 118).